https://clonwiki0.jlab.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=NersesCLONWiki - User contributions [en]2026-05-07T09:22:50ZUser contributionsMediaWiki 1.42.1https://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=4222TO DO List for Nerses2009-02-26T17:22:05Z<p>Nerses: </p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== O Attempt to change clon01 ==<br />
<br />
We have to change the in ~/.cshrc $CLAS/.setup and $CLAS/R3.24.8.2/.setup to exclude clon01 in the if branching.<br />
<br />
But, some IOCes are booting with epics account and others with clasboot. Should be standardized and documented. Sergey suggesting to have clasboot for new epics and epics for old one.<br />
<br />
<br />
<br />
<br />
== X LAC HV configuration ==<br />
<br />
Problem: LAC configs were added in the $APP/hvca/db (R3.14.8.2). But ALH for HV does not recognize them.<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
cd $APP/general/alh && make hv.alhConfig # will create alh config for HV-es.<br />
<br />
A PHONY target alh was added into $APP/hvca/db/Makefile which allows to shorten above commands to:<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
make alh # will create alh config for HV-es.<br />
<br />
<span style="color:red">If this is final we should check-in and update working version. Assumes:<br />
cvs up Makefile # to merge Makefile<br />
cvs add lac1.dat lac2.dat lac.grp<br />
cvs ci lac1.dat lac2.dat lac.grp Makefile</span><br />
<br />
== O Modify Makefiles in the $BASEB/src for new EPICS release R3.14.8.2 ==<br />
<br />
== O Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==<br />
<br />
== P CAEN EPICS support for EC ==<br />
DB and MEDM files are generated. Alarms are generated too.<br />
Should be checked if the "resore-save HV parameters" features are working.</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_Generation_of_IOC_with_different_options_and_customization_for_HallB&diff=4205EPICS: Generation of IOC with different options and customization for HallB2009-02-25T13:18:11Z<p>Nerses: </p>
<hr />
<div>To create a software IOC we will use makeBaseApp.pl and will try to customize to HallB (i.e. put them under $BASEB/src).<br />
<br />
To get some introduction one can use -h option to get the help.<br />
<br />
clon04:src> makeBaseApp.pl -h<br />
Usage:<br />
<base>/bin/<arch>/makeBaseApp.pl -h<br />
display help on command options<br />
<base>/bin/<arch>/makeBaseApp.pl -l [options]<br />
list application types<br />
<base>/bin/<arch>/makeBaseApp.pl -t type [options] [app ...]<br />
create application directories<br />
<base>/bin/<arch>/makeBaseApp.pl -i -t type [options] [ioc ...]<br />
create ioc boot directories<br />
where<br />
app Application name (the created directory will have "App" appended)<br />
ioc IOC name (the created directory will have "ioc" prepended)<br />
<br />
-a arch Set the IOC architecture for use with -i (e.g. vxWorks-68040)<br />
If arch is not specified, you will be prompted<br />
-b base Set the location of EPICS base (full path)<br />
If not specified, base path is taken from configure/RELEASE<br />
If configure does not exist, base path is taken from command<br />
-d Enable debug messages<br />
-i Specifies that ioc boot directories will be generated<br />
-l List valid application types for this installation<br />
If this is specified the other options are not used<br />
-p app Set the application name for use with -i<br />
If not specified, you will be prompted<br />
-T top Set the template top directory (where the application templates are)<br />
If not specified, top path is taken from configure/RELEASE<br />
If configure does not exist, top path is taken from environment<br />
If not found in environment, the templates from EPICS base are used<br />
-t type Set the application type (-l for a list of valid types)<br />
If not specified, type is taken from environment<br />
If not found in environment, "default" is used<br />
<br />
Environment:<br />
EPICS_MBA_DEF_APP_TYPE Application type you want to use as default<br />
EPICS_MBA_TEMPLATE_TOP Template top directory<br />
<br />
Example: Create exampleApp<br />
<base>/bin/<arch>/makeBaseApp.pl -t example example<br />
<base>/bin/<arch>/makeBaseApp.pl -i -t example example<br />
<br />
clon04:src> makeBaseApp.pl -l<br />
Valid application types are:<br />
support<br />
ioc<br />
example<br />
caClient<br />
caServer<br />
Valid iocBoot types are:<br />
example<br />
ioc</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=4204CLON Index2009-02-25T13:08:25Z<p>Nerses: </p>
<hr />
<div>[[Apache]]<br />
<br />
[[automounts]]<br />
<br />
[[Bootp]]<br />
<br />
[[Cacti]]<br />
<br />
[[CAEN A464]] caenet board (installed in sy527 mainframes)<br />
<br />
[[CAEN SY1527 Mainframe]]<br />
<br />
[[CAEN SY527 Mainframe]] and modules<br />
<br />
[[CAEN V1190]] TDC board (128 ch 100 ps)<br />
<br />
[[CAEN V1290]] TDC board (32 ch 25 ps)<br />
<br />
[[CAEN V288]]<br />
<br />
[[CAEN V775]] TDC Board<br />
<br />
[[Capfast]]<br />
<br />
[[Cisco Switches]]<br />
<br />
[[Clasweb]]<br />
<br />
[[Clasxt]]<br />
<br />
[[Clon00]]<br />
<br />
[[Clon01]]<br />
<br />
[[Clon02]]<br />
<br />
[[Clon03]]<br />
<br />
[[Clon04]]<br />
<br />
[[Clon05]]<br />
<br />
[[Clon06]]<br />
<br />
[[Clon10]]<br />
<br />
[[Clon20]]<br />
<br />
[[Clondaq1]]<br />
<br />
[[Clondaq2]]<br />
<br />
[[Clondb1]]<br />
<br />
[[Clonfs]] Main RAID System<br />
<br />
[[Clonfs1]]<br />
<br />
[[Clonfs2]]<br />
<br />
[[Clonmon]]<br />
<br />
[[Clonmon1]]<br />
<br />
[[Clonpc1]]<br />
<br />
[[Clonpc2]]<br />
<br />
[[Clonweb]]<br />
<br />
[[Clonwiki]]<br />
<br />
[[clonhp]]<br />
<br />
[[clonhp2]]<br />
<br />
[[Compcontrol CC121]]<br />
<br />
[[CycladesTS1000]]<br />
<br />
[[DATEL DVME-628]]<br />
<br />
[[DNS server]]<br />
<br />
[[Electronics Documentation]]<br />
<br />
[[EtherLite32]]<br />
<br />
[[EPICS Base Installation]]<br />
<br />
[[EPICS: Generation of IOC with different options and customization for HallB]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: vxWorks IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[EPICS: Gamma Profiler]]<br />
<br />
[[Event Monitor]]<br />
<br />
[[Fiber Channel Switches]]<br />
<br />
[[FieldPoint]]<br />
<br />
[[Foundry BigIron 15000 Switch]]<br />
<br />
[[Foundry Switches]]<br />
<br />
[[JAVA installation]]<br />
<br />
[[JLAB Discriminators]]<br />
<br />
[[Joerger VSC16]]<br />
<br />
[[HYTEC VSD2992]]<br />
<br />
[[Labeling Machines]]<br />
<br />
[[Linux Installation Procedure]]<br />
<br />
[[Linux Customization on CLON Cluster]]<br />
<br />
[[Lnf cluster]]<br />
<br />
[[Mac OS X Installation Procedure]]<br />
<br />
[[MRTG]]<br />
<br />
[[mSQL]]<br />
<br />
[[MySQL Installation]]<br />
<br />
[[MySQL Usage]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Net-SNMP]]<br />
<br />
[[NFS]]<br />
<br />
[[NIS server]]<br />
<br />
[[Nrpe]]<br />
<br />
[[Ntp]]<br />
<br />
[[OMS VME44]] by Oregon Micro Systems<br />
<br />
[[OMS VS4]] by Oregon Micro Systems<br />
<br />
[[OpenSSL]]<br />
<br />
[[PERL]]<br />
<br />
[[Procmail]]<br />
<br />
[[raidold]]<br />
<br />
[[Routing]]<br />
<br />
[[Rrdtool]]<br />
<br />
[[SBS VIPC616]]<br />
<br />
[[Serial Connections from Computer Ports]]<br />
<br />
[[Slow Controls Time History]]<br />
<br />
[[SmartSockets]]<br />
<br />
[[SNMP]]<br />
<br />
[[Software Documentation]]<br />
<br />
[[Solaris Installation Procedure]]<br />
<br />
[[Solaris Customization on CLON Cluster]]<br />
<br />
[[Solaris Patches]]<br />
<br />
[[SSH]]<br />
<br />
[[Struck SIS3801]]<br />
<br />
[[Sudo]]<br />
<br />
[[SUN Microsystems]]<br />
<br />
[[SYSTRAN VMESC5]]<br />
<br />
[[Tcl/Tk]]<br />
<br />
[[Tftp]]<br />
<br />
[[JLAB FLEXIO]]<br />
<br />
[[Troubleshooting printing]]<br />
<br />
[[UNIX Automount on CLON Cluster]]<br />
<br />
[[UPS (Uninterruptible Power Supplies)]]<br />
<br />
[[UPS CHB1]]<br />
<br />
[[UPS CHB2]]<br />
<br />
[[UPS Troubleshooting]]<br />
<br />
[[VI editor]]<br />
<br />
[[VMIC VMIVME-3122]]<br />
<br />
[[VMIC VMIVME-2120]]<br />
<br />
[[VMIC VMIVME-1129]]<br />
<br />
[[VMIC VMIVME-2232]]<br />
<br />
[[VMIC VMIVME-6015]]<br />
<br />
[[VMIC VMIVME-6016]]<br />
<br />
[[VNC]]<br />
<br />
[[WIENER]]<br />
<br />
[[Wiki]]<br />
<br />
[[Wiring]]<br />
<br />
[[X server]]<br />
<br />
[[Xycom DIO XVME-240]]<br />
<br />
[[Xycom XVME-564]]<br />
<br />
[[Xycom XVME-560]]<br />
<br />
[[ZFS]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2744TO DO List for Nerses2007-10-24T15:59:29Z<p>Nerses: /* P LAC HV configuration */</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== X LAC HV configuration ==<br />
<br />
Problem: LAC configs were added in the $APP/hvca/db (R3.14.8.2). But ALH for HV does not recognize them.<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
cd $APP/general/alh && make hv.alhConfig # will create alh config for HV-es.<br />
<br />
A PHONY target alh was added into $APP/hvca/db/Makefile which allows to shorten above commands to:<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
make alh # will create alh config for HV-es.<br />
<br />
<span style="color:red">If this is final we should check-in and update working version. Assumes:<br />
cvs up Makefile # to merge Makefile<br />
cvs add lac1.dat lac2.dat lac.grp<br />
cvs ci lac1.dat lac2.dat lac.grp Makefile</span><br />
<br />
== O Modify Makefiles in the $BASEB/src for new EPICS release R3.14.8.2 ==<br />
<br />
== O Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2729TO DO List for Nerses2007-10-24T00:40:44Z<p>Nerses: </p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== P LAC HV configuration ==<br />
<br />
Problem: LAC configs were added in the $APP/hvca/db (R3.14.8.2). But ALH for HV does not recognize them.<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
cd $APP/general/alh && make hv.alhConfig # will create alh config for HV-es.<br />
<br />
A PHONY target alh was added into $APP/hvca/db/Makefile which allows to shorten above commands to:<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
make alh # will create alh config for HV-es.<br />
<br />
<span style="color:red">If this is final we should check-in and update working version. Assumes:<br />
cvs up Makefile # to merge Makefile<br />
cvs add lac1.dat lac2.dat lac.grp<br />
cvs ci lac1.dat lac2.dat lac.grp Makefile</span><br />
<br />
<br />
== O Modify Makefiles in the $BASEB/src for new EPICS release R3.14.8.2 ==<br />
<br />
== O Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2728TO DO List for Nerses2007-10-24T00:37:33Z<p>Nerses: LAC HV configuration added</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== P LAC HV configuration ==<br />
<br />
Problem: LAC configs were added in the $APP/hvca/db (R3.14.8.2). But ALH for HV does not recognize them.<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
cd $APP/general/alh && make hv.alhConfig # will create alh config for HV-es.<br />
<br />
A PHONY target alh was added into $APP/hvca/db/Makefile which allows to shorten above commands to:<br />
cd $APP/hvca/db && \<br />
make clean && \<br />
make && \ # will make only *.alhConfig for targets listed in the default target<br />
make alh # will create alh config for HV-es.<br />
<br />
<span style="color:red">If this is final we should check-in and update working version.</span><br />
<br />
<br />
== O Modify Makefiles in the $BASEB/src for new EPICS release R3.14.8.2 ==<br />
<br />
== O Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2540TO DO List for Nerses2007-10-10T22:07:47Z<p>Nerses: </p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== O Modify Makefiles in the $BASEB/src for new EPICS release R3.14.8.2 ==<br />
<br />
== O Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2539TO DO List for Nerses2007-10-10T22:04:49Z<p>Nerses: /* Insert clonpc{1,2,3} and camac2 into ioc_alive.adl */</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== O Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2538TO DO List for Nerses2007-10-10T22:02:45Z<p>Nerses: removed duplicate entries</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2537TO DO List for Nerses2007-10-10T22:01:06Z<p>Nerses: /* O classc2 recovery */</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== X classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
Eugene Pasyuk fixed. One of motor controlling scalers was the cause.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O reboot facility for software IOC-es from ioc_alive.adl ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2529TO DO List for Nerses2007-10-10T15:49:11Z<p>Nerses: new ioc_alive.adl TODO item</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== Insert clonpc{1,2,3} and camac2 into ioc_alive.adl ==<br />
<br />
This means also to compile HallSystem from $BASEB/src on linux and vxWorks.<br />
<br />
In general assumes Makefiles in the $BASEB/src should be modified in order to be able to compile using features present in th R3.14.8.2.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O reboot facility for software IOC-es from ioc_alive.adl ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2390TO DO List for Nerses2007-10-05T14:38:55Z<p>Nerses: /* P Driver support for CAEN board 1932 */</p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
* <span style="color:red">Upload this version into CVS.</span><br />
* <span style="color:red">Then upload sy527 version for vxWorks.</span><br />
* <span style="color:red">Then upload merged sy1527-sy527 version into CVS.</span><br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O reboot facility for software IOC-es from ioc_alive.adl ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2369TO DO List for Nerses2007-10-03T19:40:23Z<p>Nerses: </p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O reboot facility for software IOC-es from ioc_alive.adl ==<br />
<br />
== O description of beam line HV channels on HallB beam line page ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2368TO DO List for Nerses2007-10-03T19:39:06Z<p>Nerses: </p>
<hr />
<div>Finished items marked by X, open items by O, and partially done items are P.<br />
<br />
== P Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
== O IOC Logging setup ==<br />
<br />
== O reboot facility fof software IOC-es from ioc_alive.adl ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2367TO DO List for Nerses2007-10-03T19:36:36Z<p>Nerses: /* O Driver support for CAEN board 1932 */</p>
<hr />
<div>Finished items marked by X, open items by O.<br />
<br />
== O Driver support for CAEN board 1932 ==<br />
<br />
Now, we have working version, which is generic for all known boards. But, because there is one software PRIMARY channel which sets limits for all channels, the interface is kind of fuzzy. Later we probably should separate 1932 board interface. The PRIMARY channel is not configured in $APP/hvca/db/<whatever>.db .So, shift takers will be obscured from internals of this board. But, experts should be aware of internals CAEN A1932. They have to connect using telnet like:<br />
telnet hvpcal 1527<br />
Then enter username and password of mainframe and change PRIMARY channel settings.<br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
== O IOC Logging setup ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2249TO DO List for Nerses2007-09-27T13:47:34Z<p>Nerses: /* O classc2 recovery */</p>
<hr />
<div>Finished items marked by X, open items by O.<br />
<br />
== O Driver support for CAEN board 1932 ==<br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
We suspect something wrong with scalers.<br />
<br />
== O IOC Logging setup ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=TO_DO_List_for_Nerses&diff=2244TO DO List for Nerses2007-09-26T01:20:24Z<p>Nerses: initial item list; softioc startup configs</p>
<hr />
<div>Finished items marked by X, open items by O.<br />
<br />
== O Driver support for CAEN board 1932 ==<br />
<br />
== X Software IOC startup configurations ==<br />
<br />
The software IOC-es are running on: <br />
clonpc1 - gamma and tpe profilers<br />
clonpc2 - HV of beam line devices (hvDvcs CAEN MF)<br />
clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)<br />
<br />
Startup directories now are $IOC/`hostname -s`. These files are used:<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2:<br />
envPaths<br />
softioc.pipe<br />
startup.all<br />
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3:<br />
envPaths <br />
softioc.pipe<br />
startup.all<br />
<br />
Startup script is /etc/init.d/softioc and it is different for each compter.<br />
Basically, because software IOC requires active STDIN (otherwise it dies), we make FIFO or named pipe, and using cat we are connecting it to the STDIN of software IOC. Besides, it is nicer than "sleep 1000d", it allows to send commands to software IOC (only once, because EOF or some signal is sent, which means exit to software IOC). This allows to avoid kill process, which leaves active the semaphore.<br />
To protect softioc.pipe files they made with read-only permissions.<br />
<br />
== O classc2 recovery ==<br />
<br />
== O IOC Logging setup ==</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=Main_Page&diff=2243Main Page2007-09-25T23:50:03Z<p>Nerses: /* CLAS Online Group At Work */ added Nerses's TODO list</p>
<hr />
<div><big>'''MediaWiki has been successfully installed.'''</big><br />
<br />
Consult the [http://meta.wikipedia.org/wiki/MediaWiki_User%27s_Guide User's Guide] for information on using the wiki software.<br />
<br />
== Getting started ==<br />
<br />
* [http://www.mediawiki.org/wiki/Help:Configuration_settings Configuration settings list]<br />
* [http://www.mediawiki.org/wiki/Help:FAQ MediaWiki FAQ]<br />
* [http://mail.wikipedia.org/mailman/listinfo/mediawiki-announce MediaWiki release mailing list]<br />
<br />
== CLAS Online Group At Work ==<br />
<br />
[[Scratch]]<br />
<br />
[[TO DO Lists]]<br />
<br />
[[TO DO List for Nerses]]<br />
<br />
[[Run Information]]<br />
<br />
[[CLON Group Meetings]]<br />
<br />
[[CLAS DAQ Upgrade]]<br />
<br />
[[Flash ADC Studies]] (in progress)<br />
<br />
[[DVCS Trigger System]]<br />
<br />
[[CLAS12 Trigger System Design]] (in progress)<br />
<br />
== CLAS Online System Documentation ==<br />
<br />
[[CLON Cluster System Administration]]<br />
<br />
[[CLAS Online Software]]<br />
<br />
[[CLAS Online Hardware]]<br />
<br />
== CLAS Online System Index ==<br />
<br />
[[CLON Index]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=1564CLON Index2007-01-09T21:59:18Z<p>Nerses: </p>
<hr />
<div>[[Clonweb]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[EPICS: Gamma Profiler]]<br />
<br />
[[MRTG]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Nrpe]]<br />
<br />
[[OpenSSL]]<br />
<br />
[[Solaris Installation Procedure]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_CVS_usage_examples&diff=1556EPICS: CVS usage examples2007-01-09T02:05:05Z<p>Nerses: </p>
<hr />
<div>=Checking out sources=<br />
We will create temporary directory '''t1''' and will check out '''CAEN_HV''' and '''bigsub''' sources into it.<br />
mkdir t1<br />
cd t1<br />
cvs co baseB/src/CAEN_HV baseB/src/bigsub<br />
<br />
=Tagging a new branch=<br />
We will tag them with new branch name R3-14-8-2 ( ''.:;'' symbols are not allowed in the tag names).<br />
cd baseB/src<br />
cvs tag -b R3-14-8-2 (create tag)<br />
cvs up -r R3-14-8-2 (update to tagged version)<br />
<br />
=Adding new files=<br />
<br />
Add, modify or replace your files in the corresponding directories.<br />
To find out which files should be added into cvs:<br />
clonpc3:bigsub> find -type f -maxdepth 1 -exec cvs st {} \; |grep Unknown<br />
File: a_out.h Status: Unknown<br />
<br />
This command finds the regular files in current directory and for each file found does cvs status and greps for Unknown status. Then we need add files into cvs<br />
<br />
cvs add a_out.h<br />
<br />
<br />
=Commiting changes=<br />
<br />
cvs ci -m "This is bigsub record version for CAEN HV, it is not compatiable with standard bigsub record."<br />
<br />
=Check out the branch=<br />
<br />
cvs co -r R3-14-8-2<br />
<br />
=Update the branch=<br />
<br />
cvs up -r R3-14-8-2<br />
<br />
=Merge branch with main trunk=<br />
<br />
Use -j option to update, which stands for ''join''.<br />
cvs co baseB/src/bigsub<br />
cvs up -jR3-14-8-2</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_CVS_usage_examples&diff=1555EPICS: CVS usage examples2007-01-09T00:08:17Z<p>Nerses: </p>
<hr />
<div>=Checking out sources=<br />
mkdir t1<br />
cd t1<br />
cvs co baseB/src/CAEN_HV baseB/src/bigsub (checkout CAEN_HV and bigsub sources)<br />
<br />
=Tagging a new branch=<br />
cvs tag -b R3-14-8-2 (create tag)<br />
cvs up -r R3-14-8-2 (update to tagged version)<br />
cd baseB/src<br />
<br />
=Adding new files=<br />
<br />
Add, modify or replace your files in the corresponding directories.<br />
To find out which files should be added into cvs:<br />
clonpc3:bigsub> find -type f -maxdepth 1 -exec cvs st {} \; |grep Unknown<br />
File: a_out.h Status: Unknown<br />
<br />
This command finds the regular files in current directory and for each file found does cvs status and greps for Unknown status. Then we need add files into cvs<br />
<br />
cvs add a_out.h<br />
<br />
<br />
=Commiting changes=<br />
<br />
cvs ci -m "This is bigsub record version for CAEN HV, it is not compatiable with standard bigsub record." <br />
<br />
For example:<br />
cvs update -A<br />
touch a b c<br />
cvs add a b c ; cvs ci -m "added" a b c<br />
cvs tag -b branchtag<br />
cvs update -r branchtag<br />
touch d ; cvs add d<br />
rm a ; cvs rm a<br />
cvs ci -m "added d, removed a"<br />
cvs update -A<br />
cvs update -jbranchtag</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=1554CLON Index2007-01-08T21:24:53Z<p>Nerses: </p>
<hr />
<div>[[Clonweb]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[EPICS: CVS usage examples]]<br />
<br />
[[MRTG]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Nrpe]]<br />
<br />
[[OpenSSL]]<br />
<br />
[[Solaris Installation Procedure]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=CLON_Index&diff=1552CLON Index2007-01-08T20:34:26Z<p>Nerses: </p>
<hr />
<div>[[Clonweb]]<br />
<br />
[[EPICS: Software IOC]]<br />
<br />
[[EPICS: Software IOC for CAEN HV]]<br />
<br />
[[EPICS: generation of DBs and GUIs for HV]]<br />
<br />
[[Howto add a new branch to CVS. An example for CAEN HV software]]<br />
<br />
[[MRTG]]<br />
<br />
[[Nagios]]<br />
<br />
[[Nagios Plugins]]<br />
<br />
[[Nrpe]]<br />
<br />
[[OpenSSL]]<br />
<br />
[[Solaris Installation Procedure]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_Software_IOC&diff=1488EPICS: Software IOC2007-01-06T02:57:56Z<p>Nerses: </p>
<hr />
<div>Software IOC is the process running on Linux or Solaris.<br />
For initial setting do following:<br />
<br />
ssh boiarino@clonpc1<br />
cd $CLAS/R3.14.8.2<br />
source .setup (usually done by $CLAS/.setup)<br />
cd $CLAS/R3.14.8.2/EPICS (this is the 'epicsB' directory)<br />
source .setup (usually done by $CLAS/R3.14.8.2/.setup above)<br />
cd baseB (or 'cd $BASEB')<br />
<br />
New application can be done using 'makeBaseApp.pl' script (More detailed explained [http://www.aps.anl.gov/asd/controls/epics/EpicsDocumentation/AppDevManuals/iocScm-3.13.2/creatingTops.html here] and nicer [http://www-hades.gsi.de/scs/appl_hints.html here]). To see possible application types use following:<br />
<br />
makeBaseApp.pl -l<br />
<br />
It will show:<br />
<br />
Valid application types are:<br />
support<br />
ioc<br />
example<br />
caClient<br />
caServer<br />
Valid iocBoot types are:<br />
example<br />
ioc<br />
<br />
Following command will create new type 'example' application named 'test1' (it will NOT create new Makefile and configure/ directory if they exists already, otherwise it will !):<br />
<br />
makeBaseApp.pl -b $EPICS_BASE -t example test1<br />
<br />
It will create subdirectory test1App with appropriate contents; do following:<br />
<br />
cd test1App<br />
make<br />
<br />
To make boot script do following:<br />
<br />
makeBaseApp.pl -b $EPICS_BASE -i -t example test1<br />
<br />
Following dialog:<br />
<br />
The following target architectures are available in base:<br />
solaris-sparc<br />
vxWorks-ppc604_long<br />
solaris-x86<br />
linux-x86<br />
What architecture do you want to use? linux-x86<br />
The following applications are available:<br />
test1<br />
What application should the IOC(s) boot?<br />
The default uses the IOC's name, even if not listed above.<br />
Application name? test1<br />
<br />
It will do following:<br />
<br />
create iocBoot/ and iocBoot/Makefile if do not exists already<br />
create iocBoot/iostest1 with appropriate contents<br />
creade db/ if does not exist already (?)<br />
copy *.db files from test1App/Db/ to db/ <br />
create dbd/ if does not exist already (?)<br />
copy some (?) *.dbd files from test1App/ to dbd/ (xxxRecord.dbd, xxxSupport.dbd)<br />
create dbd/test1.dbd (copies some templete from base ???)<br />
create include/ if does not exist (?)<br />
copy xxxRecord.h file to include/ (from some templete ?) (corresponds to some dbd file ?)<br />
copy libxxxSupport.a and libxxxSupport.so to lib/linux-x86/ (or whatever platform is)<br />
<br />
To create environment envPaths:<br />
<br />
cd iocBoot<br />
make<br />
<br />
It will create ioctest1/envPaths<br />
<br />
To start IOC:<br />
<br />
cd ioctest1/<br />
chmod 755 st.cmd<br />
./st.cmd<br />
<br />
Following output:<br />
<br />
#!../../bin/linux-x86/test1<br />
## You may have to change test1 to something else<br />
## everywhere it appears in this file<br />
< envPaths<br />
epicsEnvSet(ARCH,"linux-x86")<br />
epicsEnvSet(IOC,"ioctest1")<br />
epicsEnvSet(TOP,"/usr/local/clas/devel/R3.14.8.2/EPICS/baseB")<br />
cd /usr/local/clas/devel/R3.14.8.2/EPICS/baseB<br />
## Register all support components<br />
dbLoadDatabase("dbd/test1.dbd")<br />
test1_registerRecordDeviceDriver(pdbbase)<br />
## Load record instances<br />
dbLoadRecords("db/dbExample1.db","user=boiarinoHost")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=1,scan=1 second")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=2,scan=2 second")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=3,scan=5 second")<br />
dbLoadRecords("db/dbSubExample.db","user=boiarinoHost")<br />
## Set this to see messages from mySub<br />
#var mySubDebug 1<br />
cd /usr/local/clas/devel/R3.14.8.2/EPICS/baseB/iocBoot/ioctest1<br />
iocInit()<br />
Starting iocInit<br />
############################################################################<br />
### EPICS IOC CORE built on Sep 21 2006<br />
### EPICS R3.14.8.2 $R3-14-8-2$ $2006/01/06 15:55:13$<br />
############################################################################<br />
iocInit: All initialization complete<br />
## Start any sequence programs<br />
#seq sncExample,"user=boiarinoHost"<br />
epics><br />
<br />
To list all available channels:<br />
<br />
epics> dbl<br />
boiarinoHost:aiExample<br />
boiarinoHost:aiExample1<br />
boiarinoHost:aiExample2<br />
boiarinoHost:aiExample3<br />
boiarinoHost:calcExample<br />
boiarinoHost:calcExample1<br />
boiarinoHost:calcExample2<br />
boiarinoHost:calcExample3<br />
boiarinoHost:compressExample<br />
boiarinoHost:subExample<br />
boiarinoHost:xxxExample<br />
epics><br />
<br />
Use 'help' on 'epics>' prompt to get full list of commands.<br />
<br />
Channels can be accessed now, for example type on another machine:<br />
<br />
caget boiarinoHost:aiExample<br />
<br />
It will return digit from 0 to 9 every time it called.<br />
<br />
Existing IOCs have different structure, they can be found in baseB/src/, for example see inside CAEN_HV/.<br />
To make it realy useful *.db files and medm GUI must be generated - see corresponding sections. For example: [[EPICS: generation of DBs and GUIs for HV]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_Software_IOC&diff=1487EPICS: Software IOC2007-01-06T02:56:24Z<p>Nerses: </p>
<hr />
<div>Software IOC is the process running on Linux or Solaris.<br />
For initial setting do following:<br />
<br />
ssh boiarino@clonpc1<br />
cd $CLAS/R3.14.8.2<br />
source .setup (usually done by $CLAS/.setup)<br />
cd $CLAS/R3.14.8.2/EPICS (this is the 'epicsB' directory)<br />
source .setup (usually done by $CLAS/R3.14.8.2/.setup above)<br />
cd baseB (or 'cd $BASEB')<br />
<br />
New application can be done using 'makeBaseApp.pl' script (More detailed explained [http://www.aps.anl.gov/asd/controls/epics/EpicsDocumentation/AppDevManuals/iocScm-3.13.2/creatingTops.html here] and [http://www-hades.gsi.de/scs/appl_hints.html here]). To see possible application types use following:<br />
<br />
makeBaseApp.pl -l<br />
<br />
It will show:<br />
<br />
Valid application types are:<br />
support<br />
ioc<br />
example<br />
caClient<br />
caServer<br />
Valid iocBoot types are:<br />
example<br />
ioc<br />
<br />
Following command will create new type 'example' application named 'test1' (it will NOT create new Makefile and configure/ directory if they exists already, otherwise it will !):<br />
<br />
makeBaseApp.pl -b $EPICS_BASE -t example test1<br />
<br />
It will create subdirectory test1App with appropriate contents; do following:<br />
<br />
cd test1App<br />
make<br />
<br />
To make boot script do following:<br />
<br />
makeBaseApp.pl -b $EPICS_BASE -i -t example test1<br />
<br />
Following dialog:<br />
<br />
The following target architectures are available in base:<br />
solaris-sparc<br />
vxWorks-ppc604_long<br />
solaris-x86<br />
linux-x86<br />
What architecture do you want to use? linux-x86<br />
The following applications are available:<br />
test1<br />
What application should the IOC(s) boot?<br />
The default uses the IOC's name, even if not listed above.<br />
Application name? test1<br />
<br />
It will do following:<br />
<br />
create iocBoot/ and iocBoot/Makefile if do not exists already<br />
create iocBoot/iostest1 with appropriate contents<br />
creade db/ if does not exist already (?)<br />
copy *.db files from test1App/Db/ to db/ <br />
create dbd/ if does not exist already (?)<br />
copy some (?) *.dbd files from test1App/ to dbd/ (xxxRecord.dbd, xxxSupport.dbd)<br />
create dbd/test1.dbd (copies some templete from base ???)<br />
create include/ if does not exist (?)<br />
copy xxxRecord.h file to include/ (from some templete ?) (corresponds to some dbd file ?)<br />
copy libxxxSupport.a and libxxxSupport.so to lib/linux-x86/ (or whatever platform is)<br />
<br />
To create environment envPaths:<br />
<br />
cd iocBoot<br />
make<br />
<br />
It will create ioctest1/envPaths<br />
<br />
To start IOC:<br />
<br />
cd ioctest1/<br />
chmod 755 st.cmd<br />
./st.cmd<br />
<br />
Following output:<br />
<br />
#!../../bin/linux-x86/test1<br />
## You may have to change test1 to something else<br />
## everywhere it appears in this file<br />
< envPaths<br />
epicsEnvSet(ARCH,"linux-x86")<br />
epicsEnvSet(IOC,"ioctest1")<br />
epicsEnvSet(TOP,"/usr/local/clas/devel/R3.14.8.2/EPICS/baseB")<br />
cd /usr/local/clas/devel/R3.14.8.2/EPICS/baseB<br />
## Register all support components<br />
dbLoadDatabase("dbd/test1.dbd")<br />
test1_registerRecordDeviceDriver(pdbbase)<br />
## Load record instances<br />
dbLoadRecords("db/dbExample1.db","user=boiarinoHost")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=1,scan=1 second")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=2,scan=2 second")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=3,scan=5 second")<br />
dbLoadRecords("db/dbSubExample.db","user=boiarinoHost")<br />
## Set this to see messages from mySub<br />
#var mySubDebug 1<br />
cd /usr/local/clas/devel/R3.14.8.2/EPICS/baseB/iocBoot/ioctest1<br />
iocInit()<br />
Starting iocInit<br />
############################################################################<br />
### EPICS IOC CORE built on Sep 21 2006<br />
### EPICS R3.14.8.2 $R3-14-8-2$ $2006/01/06 15:55:13$<br />
############################################################################<br />
iocInit: All initialization complete<br />
## Start any sequence programs<br />
#seq sncExample,"user=boiarinoHost"<br />
epics><br />
<br />
To list all available channels:<br />
<br />
epics> dbl<br />
boiarinoHost:aiExample<br />
boiarinoHost:aiExample1<br />
boiarinoHost:aiExample2<br />
boiarinoHost:aiExample3<br />
boiarinoHost:calcExample<br />
boiarinoHost:calcExample1<br />
boiarinoHost:calcExample2<br />
boiarinoHost:calcExample3<br />
boiarinoHost:compressExample<br />
boiarinoHost:subExample<br />
boiarinoHost:xxxExample<br />
epics><br />
<br />
Use 'help' on 'epics>' prompt to get full list of commands.<br />
<br />
Channels can be accessed now, for example type on another machine:<br />
<br />
caget boiarinoHost:aiExample<br />
<br />
It will return digit from 0 to 9 every time it called.<br />
<br />
Existing IOCs have different structure, they can be found in baseB/src/, for example see inside CAEN_HV/.<br />
To make it realy useful *.db files and medm GUI must be generated - see corresponding sections. For example: [[EPICS: generation of DBs and GUIs for HV]]</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_generation_of_DBs_and_GUIs_for_HV&diff=1484EPICS: generation of DBs and GUIs for HV2007-01-06T02:14:02Z<p>Nerses: </p>
<hr />
<div>Following procedure generates *.db and *.adl/*.alh files for High Voltage applications.<br />
<br />
cd $APP/hvca/db/<br />
<br />
Create *.dat file with following format:<br />
<br />
clonpc1:db> more caen.dat<br />
CAEN_1_00 02 1 1 01 01 03 00 -1200.0 1.5 1.3 121.5 486.0 2550.0 -2500.0<br />
CAEN_1_01 02 1 1 01 01 03 01 -1200.0 1.5 1.3 121.5 486.0 2550.0 -2500.0<br />
CAEN_1_02 02 1 1 01 01 03 02 -1200.0 1.5 1.3 121.5 486.0 2550.0 -2500.0<br />
CAEN_1_03 02 1 1 01 01 03 03 -1200.0 1.5 1.3 121.5 486.0 2550.0 -2500.0<br />
.....................................<br />
<br />
Columns have following meaning (NEED CHECK !):<br />
<br />
1 - group name (channel name, will be used as part of EPICS channel access variable names)<br />
2 - group number<br />
3 - allow (?)<br />
4 - ioc number<br />
5 - mainframe address (for Lecroy by jumpers, for CAEN by IP, test mainframes must be >100 ???)<br />
6 - slot/card number<br />
7 - submodule (?)<br />
8 - channel number<br />
9 - voltage (demand, V)<br />
10 - mvdz (measured voltage dead-zone, V)<br />
11 - mcdz (measuerd current dead-zone, uA?)<br />
12 - rump up speed, V/s<br />
13 - rump down speed, V/s<br />
14 - tc (trip current, uA?)<br />
15 - maximum voltage (max, V)<br />
<br />
Second input file is *.grp, for example caen.grp:<br />
<br />
clonpc1:db> more caen.grp<br />
1 CAEN_7<br />
<br />
First column is group number and second one is group name. It will be first two columns on medm screen.<br />
<br />
Makefile must be manually adjusted for every new *.dat file. It is possible to combine several *.dat file in one - see inside Makefile.<br />
<br />
To generate all necessary file type 'make <filename without extension>', for example if file name is 'caen.dat', type:<br />
<br />
make caen<br />
<br />
Following output fill shows up:<br />
<br />
clonpc1:db> make caen<br />
./dat2db.pl caen<br />
echo caen | /usr/local/clas/devel/R3.14.8.2/EPICS/app/hvca/bin/hv_adl<br />
Input name of hv data file (omit the extension '.dat') : <br />
WORKING ON GROUP #1<br />
Initializing variables to default values.<br />
Creating file: caen_CAEN_7_1.adl<br />
Initializing variables to default values.<br />
Creating file: caen_CAEN_7_param_1.adl<br />
Initializing variables to default values.<br />
Creating file: caen.adl<br />
./dat2req.pl caen<br />
chmod +x caen*.csh<br />
test -d ../medm/adl || mkdir ../medm/adl<br />
test -d ../req || mkdir ../req<br />
mv caen*.adl ../medm/adl<br />
mv caen*.snap ../req<br />
mv caen*.csh ../medm/adl<br />
mv caen*.alarms ../medm/adl<br />
test -d ../medm/alh || mkdir ../medm/alh<br />
mv caen*.alhConfig* ../medm/alh<br />
<br />
Following files willbe produced:<br />
<br />
caen_01.db<br />
../medm/adl/caen.adl<br />
.................adl<br />
../medm/alh/caen_CAEN_7.alhConfig<br />
../medm/alh/caen_mf_01_01.alhConfig_mf<br />
<br />
Now copy generated *.db files into final destination where it will be picked up by IOC startup script, for example:<br />
<br />
cp caen_01.db $BASEB/src/CAEN_HV/IocShell/<br />
<br />
Create appropriate links to our medm files from standatd place:<br />
<br />
cd $APP/medm<br />
make<br />
<br />
Create appropriate links to our alh files from standatd place:<br />
<br />
cd $APP/alh<br />
make</div>Nerseshttps://clonwiki0.jlab.org/wiki/index.php?title=EPICS:_Software_IOC&diff=1483EPICS: Software IOC2007-01-06T01:17:40Z<p>Nerses: </p>
<hr />
<div>Software IOC is the process running on Linux or Solaris.<br />
For initial setting do following:<br />
<br />
ssh boiarino@clonpc1<br />
cd $CLAS/R3.14.8.2<br />
source .setup (usually done by $CLAS/.setup)<br />
cd $CLAS/R3.14.8.2/EPICS (this is the 'epicsB' directory)<br />
source .setup (usually done by $CLAS/R3.14.8.2/.setup above)<br />
cd baseB (or 'cd $BASEB')<br />
<br />
New application can be done using 'makeBaseApp.pl' script (More detailed explained [http://www-hades.gsi.de/scs/appl_hints.html here]). To see possible application types use following:<br />
<br />
makeBaseApp.pl -l<br />
<br />
It will show:<br />
<br />
Valid application types are:<br />
support<br />
ioc<br />
example<br />
caClient<br />
caServer<br />
Valid iocBoot types are:<br />
example<br />
ioc<br />
<br />
Following command will create new type 'example' application named 'test1' (it will NOT create new Makefile and configure/ directory if they exists already, otherwise it will !):<br />
<br />
makeBaseApp.pl -b $EPICS_BASE -t example test1<br />
<br />
It will create subdirectory test1App with appropriate contents; do following:<br />
<br />
cd test1App<br />
make<br />
<br />
To make boot script do following:<br />
<br />
makeBaseApp.pl -b $EPICS_BASE -i -t example test1<br />
<br />
Following dialog:<br />
<br />
The following target architectures are available in base:<br />
solaris-sparc<br />
vxWorks-ppc604_long<br />
solaris-x86<br />
linux-x86<br />
What architecture do you want to use? linux-x86<br />
The following applications are available:<br />
test1<br />
What application should the IOC(s) boot?<br />
The default uses the IOC's name, even if not listed above.<br />
Application name? test1<br />
<br />
It will do following:<br />
<br />
create iocBoot/ and iocBoot/Makefile if do not exists already<br />
create iocBoot/iostest1 with appropriate contents<br />
creade db/ if does not exist already (?)<br />
copy *.db files from test1App/Db/ to db/ <br />
create dbd/ if does not exist already (?)<br />
copy some (?) *.dbd files from test1App/ to dbd/ (xxxRecord.dbd, xxxSupport.dbd)<br />
create dbd/test1.dbd (copies some templete from base ???)<br />
create include/ if does not exist (?)<br />
copy xxxRecord.h file to include/ (from some templete ?) (corresponds to some dbd file ?)<br />
copy libxxxSupport.a and libxxxSupport.so to lib/linux-x86/ (or whatever platform is)<br />
<br />
To create environment envPaths:<br />
<br />
cd iocBoot<br />
make<br />
<br />
It will create ioctest1/envPaths<br />
<br />
To start IOC:<br />
<br />
cd ioctest1/<br />
chmod 755 st.cmd<br />
./st.cmd<br />
<br />
Following output:<br />
<br />
#!../../bin/linux-x86/test1<br />
## You may have to change test1 to something else<br />
## everywhere it appears in this file<br />
< envPaths<br />
epicsEnvSet(ARCH,"linux-x86")<br />
epicsEnvSet(IOC,"ioctest1")<br />
epicsEnvSet(TOP,"/usr/local/clas/devel/R3.14.8.2/EPICS/baseB")<br />
cd /usr/local/clas/devel/R3.14.8.2/EPICS/baseB<br />
## Register all support components<br />
dbLoadDatabase("dbd/test1.dbd")<br />
test1_registerRecordDeviceDriver(pdbbase)<br />
## Load record instances<br />
dbLoadRecords("db/dbExample1.db","user=boiarinoHost")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=1,scan=1 second")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=2,scan=2 second")<br />
dbLoadRecords("db/dbExample2.db","user=boiarinoHost,no=3,scan=5 second")<br />
dbLoadRecords("db/dbSubExample.db","user=boiarinoHost")<br />
## Set this to see messages from mySub<br />
#var mySubDebug 1<br />
cd /usr/local/clas/devel/R3.14.8.2/EPICS/baseB/iocBoot/ioctest1<br />
iocInit()<br />
Starting iocInit<br />
############################################################################<br />
### EPICS IOC CORE built on Sep 21 2006<br />
### EPICS R3.14.8.2 $R3-14-8-2$ $2006/01/06 15:55:13$<br />
############################################################################<br />
iocInit: All initialization complete<br />
## Start any sequence programs<br />
#seq sncExample,"user=boiarinoHost"<br />
epics><br />
<br />
To list all available channels:<br />
<br />
epics> dbl<br />
boiarinoHost:aiExample<br />
boiarinoHost:aiExample1<br />
boiarinoHost:aiExample2<br />
boiarinoHost:aiExample3<br />
boiarinoHost:calcExample<br />
boiarinoHost:calcExample1<br />
boiarinoHost:calcExample2<br />
boiarinoHost:calcExample3<br />
boiarinoHost:compressExample<br />
boiarinoHost:subExample<br />
boiarinoHost:xxxExample<br />
epics><br />
<br />
Use 'help' on 'epics>' prompt to get full list of commands.<br />
<br />
Channels can be accessed now, for example type on another machine:<br />
<br />
caget boiarinoHost:aiExample<br />
<br />
It will return digit from 0 to 9 every time it called.<br />
<br />
Existing IOCs have different structure, they can be found in baseB/src/, for example see inside CAEN_HV/.<br />
To make it realy useful *.db files and medm GUI must be generated - see corresponding sections. For example: [[EPICS: generation of DBs and GUIs for HV]]</div>Nerses