Hello!

After many firmware changes, driver fixes, and head scratches, the GAB is now fully timed in with the TAB and ADF in the online environment.

For proof, I bring the "head" of a L2/L3 buffer for a BC=10 L1
accepted event read from diagnostic memory on the GAB:

S30 level 2 output memory:
status:  0
bc:      10
...

As you can see, it is BC=10 as it should be.  Just one number, but it has made it's way from the ADFs into the TAB SWA chips, then to the TAB global chip, then to a GAB LVDS chip, then into the GAB S30 chip, and now it is being sent off to L3.

I also made many cross checks that the parameters behave as they are supposed to when adjusted.  As always, you can see the gory details at:

http://www-clued0.fnal.gov/~mulhearn/log/l1cal/

This means we are ready to make a real latency measurement into the Framework, and that we are ready to start sending our own L1Cal2B triggers!

cheers,
mike