Re: hv frontend

[Brendan Kiburg <kiburg@npl.uiuc.edu>]

Hello again,
   Steve, thanks for the useful information.  After some fighting with 
the ODB, I found the keys and made the appropriate mapping changes.  The 
frontend runs and things seem to be correct. 
Thanks again for the help.

Brendan

>My guess is that it is trying to open the wrong serial port.
>The message about database corruption may not be a big deal.
>To have it use the ODB on cheetah, I think you have to set
>the environment variables MIDAS_SERVER_HOST and MIDAS_EXPT
>(or something like that) to cheetah and mucap(?), respectively.
>Maybe MIDAS_DIR has to be undefined as well.
>
>Regarding the serial port: it looks like this is defined in
>one of the ODB keys for this device.  The experim.h file
>in the directory, snake:/home/data/daq/slow/nitronic-hv,
>initializes these values, apparently to "/dev/ttyUSB4,"
>"/dev/ttyUSB5," and "/dev/ttyUSB6."
>
>Good luck!
>Steven
>On Thu, Sep 22, 2005 at 11:44:49AM -0500, Brendan Kiburg wrote:
>  
>
>>> Dear Steven and Fred, 
>>>   I have been able to execute the frontend program, but I recieve the
>>> following errors as the program tries to start up:
>>> 
>>> [data@snake nitronic-hv]$ ./hv_frontend
>>> Frontend name          :     HV Frontend
>>> Event buffer size      :     100000
>>> Buffer allocation      : 2 x 100000
>>> System max event size  :     8388608
>>> User max event size    :     10000
>>> User max frag. size    :     5242880
>>> # of events per buffer :     10
>>> 
>>> Connect to experiment ...[odb.c:858:db_validate_key] Warning: database
>>> corruptio                                            n, key
>>> "/System/Tmp/28843O", first_key 0xFFFDEFC0
>>> OK
>>> Init hardware...rs232_open: No such file or directory
>>> 
>>> Is this related to setting the proper midas path for the odb?  If so, do
>>> we have to make it point to cheetah in some way?
>>> 
>>> Also, when the hv frontend finishes its initialization, it displays the
>>> following information :
>>> 
>>> HV Frontend connected to <local>. Press "!" to exit
>>> 18:19:30
>>> ================================================================================
>>> Run status:   Stopped    Run number 2
>>> ================================================================================
>>> Equipment     Status     Events     Events/sec Rate[kB/s] ODB->FE
>>> FE->ODB
>>> --------------------------------------------------------------------------------
>>> HV            HW Error   0          0.0        0.0        0          0
>>> 
>>> I assume this just confirms that the hardware didn't initialize properly,
>>> but I wasn't sure if it contained any other information that might be
>>> useful to you.
>>> 
>>> Any thoughts or comments would be appreciated.
>>> Best regards,
>>> Brendan
>>    
>>
>  
>
>