TO DO List for Nerses: Difference between revisions
No edit summary |
|||
| Line 1: | Line 1: | ||
Finished items marked by X, open items by O. | Finished items marked by X, open items by O, and partially done items are P. | ||
== | == P Driver support for CAEN board 1932 == | ||
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: | 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: | ||
| Line 37: | Line 37: | ||
== O IOC Logging setup == | == O IOC Logging setup == | ||
== O reboot facility fof software IOC-es from ioc_alive.adl == | |||
Revision as of 14:39, 3 October 2007
Finished items marked by X, open items by O, and partially done items are P.
P Driver support for CAEN board 1932
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:
telnet hvpcal 1527
Then enter username and password of mainframe and change PRIMARY channel settings.
X Software IOC startup configurations
The software IOC-es are running on:
clonpc1 - gamma and tpe profilers clonpc2 - HV of beam line devices (hvDvcs CAEN MF) clonpc3 - test setups for CAEN HV MF-es (hvPCal and hvTest)
Startup directories now are $IOC/`hostname -s`. These files are used:
/usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc1: envPaths softioc.pipe startup.all /usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc2: envPaths softioc.pipe startup.all /usr/local/clas/release/current/R3.14.8.2/EPICS/ioc/clonpc3: envPaths softioc.pipe startup.all
Startup script is /etc/init.d/softioc and it is different for each compter. 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. To protect softioc.pipe files they made with read-only permissions.
O classc2 recovery
We suspect something wrong with scalers.