Re: Berkeley FADC board

[Frederick Gray <fegray@berkeley.edu>]

> Great...the new firmware should be ready to go now.   The next step is to move 
> it back to the data-taking position and try it out.  The power should be
> connected after the other cables, and while the DAQ is not running.
> If the problem isn't fixed, then I'll ask you to look at test point TP2 on a
> scope, so you might want to locate it while you're installing the board.

Hello again, 

As I haven't heard back from you, I'm going to bed now.  If you have 
a chance, please try to set up the board in the data-taking position tonight.  
If you run "/usr/sbin/tcpdump ether proto 0x0b04" as root on cheetah,
you will see the data coming in.  The first word of each packet is the
data length.  A length of zero indicates a start/stop packet.  If you see 
packets with hundreds of bytes, they are probably "good" data.  You should be 
able to tell whether the "good" data packets keep arriving for more than a few 
minutes after you power the module.  If not, it would be very
interesting to know the state of TP2 (look at it with a scope) when 
"good" data has stopped flowing.

Thanks,

-- Fred

-- Fred Gray / Visiting Postdoctoral Researcher                 --
-- Department of Physics / University of California, Berkeley   --
-- fegray@berkeley.edu / phone 510-642-2438 / fax 510-642-9811  --